projects / qt4-x11.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a28e328) | patch
Fix logic for figuring out what ConfigureNotify positions can be trusted
authorOwen W. Taylor <otaylor@fishsoup.net>
Mon, 17 Oct 2011 21:27:43 +0000 (17:27 -0400)
committerDmitry Shachnev <mitya57@debian.org>
Fri, 12 Apr 2019 20:10:28 +0000 (21:10 +0100)
commitb8428d845d3701894d6f03284ff98c242a0504c6
tree1fa76060c2e3e2af25194b0b4406101b5998dba1tree | snapshot
parenta28e328b2a0351e288c17952830b01a1078d2ff4commit | diff
Fix logic for figuring out what ConfigureNotify positions can be trusted

When reading ahead in the queue for ConfigureNotify events, it's necessary
to look for intermediate ReparentNotify events as well, since they will
determine whether the position in the event can be trusted or not.

Bug: https://bugreports.qt.nokia.com/browse/QTBUG-21900

Gbp-Pq: Name QTBUG-21900_Buttons_in_Qt_applications_not_clickable_when_run_under_gnome-shell.patch
src/gui/kernel/qapplication_x11.cpp diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.